Skip to content

chore: change snapshot release#1993

Merged
tatomyr merged 4 commits intov2from
chore/change-snapshot-release
Mar 7, 2025
Merged

chore: change snapshot release#1993
tatomyr merged 4 commits intov2from
chore/change-snapshot-release

Conversation

@tatomyr
Copy link
Collaborator

@tatomyr tatomyr commented Mar 6, 2025 •
edited
Loading

What/Why/How?

Simplified the snapshot release process to avoid extra PRs and comparisons to main.
Now, only code from a labeled branch will be released under the snapshot tag.
No one outside the organization can add a label anyway.

Also, made run the changeset check only on PRs to the main branch.

Testing

Test in this PR.

Security

  • Security impact of change has been considered
  • Code follows company security practices and guidelines

@changeset-bot
Copy link

changeset-bot bot commented Mar 6, 2025 •
edited
Loading

⚠️ No Changeset found

Latest commit: a8805bf

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@tatomyr tatomyr changed the title Chore/change snapshot release chore: change snapshot release Mar 6, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Mar 6, 2025 •
edited
Loading

Command Mean [ms] Min [ms] Max [ms] Relative
redocly lint packages/core/src/benchmark/benches/rebilly.yaml 962.1 ± 21.6 935.9 1002.3 1.02 ± 0.03
redocly-next lint packages/core/src/benchmark/benches/rebilly.yaml 947.0 ± 13.3 932.4 967.1 1.00

@tatomyr tatomyr force-pushed the chore/change-snapshot-release branch from aaa0776 to 4c3fbbc Compare March 6, 2025 21:19
@tatomyr tatomyr changed the base branch from main to v2 March 6, 2025 21:20
@github-actions
Copy link
Contributor

github-actions bot commented Mar 6, 2025 •
edited
Loading

Coverage report

St.❔
 Category Percentage Covered / Total
🟢 Statements 80.91% 7036/8696
🟡 Branches 69.71% 2934/4209
🟡 Functions 76.4% 1149/1504
🟢 Lines 81.33% 6711/8252

Test suite run success

1338 tests passing in 193 suites.

Report generated by 🧪jest coverage report action from a8805bf

@tatomyr tatomyr added the snapshot Create experimental release PR label Mar 6, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Mar 6, 2025

📦 A new experimental 🧪 version v0.0.0-snapshot.1741296362 of Redocly CLI has been published for testing.

Install with NPM:

npm install @redocly/cli@0.0.0-snapshot.1741296362
# or
npm install @redocly/openapi-core@0.0.0-snapshot.1741296362
# or
npm install @redocly/respect-core@0.0.0-snapshot.1741296362

⚠️ Note: This is a development build and may contain unstable features.

@tatomyr tatomyr marked this pull request as ready for review March 6, 2025 21:49
@tatomyr tatomyr requested a review from a team as a code owner March 6, 2025 21:49
@tatomyr tatomyr merged commit e0cc5d9 into v2 Mar 7, 2025
34 checks passed
@tatomyr tatomyr deleted the chore/change-snapshot-release branch March 7, 2025 09:51
tatomyr added a commit that referenced this pull request Mar 19, 2025
@tatomyr
chore: change snapshot release (#1993)
684db3e
tatomyr added a commit that referenced this pull request Mar 20, 2025
@tatomyr
chore: change snapshot release (#1993)
6220968
andriimredocly pushed a commit that referenced this pull request Mar 24, 2025
@tatomyr @andriimredocly
chore: change snapshot release (#1993)
f90e0ec
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@DmitryAnansky DmitryAnansky DmitryAnansky approved these changes

Assignees

No one assigned

Labels

snapshot Create experimental release PR

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@tatomyr @DmitryAnansky